• The following instructions are accomplished through Windows Explorer.
• Perform each test by performing the steps specified by the instructions.  
• Evaluate the results of each step by comparing them with results described in the Documentation column. 

Instructions 1
The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation directory named "saspgm".

2. Right mouse click on addseq1.sas and select "Batch Submit".

3. Review the addseq1.log and verify that the following messages are produce corresponding to each test.

   • Test (A)
     ERROR: [addseq] is missing required parameter DATA. 

   • Test (B)
     ERROR: [addseq] is missing required parameter RDOMAIN.

   • Test (C)
     ERROR: [addseq] is missing required parameter USUBJID. 
     

Instructions 2
The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation directory named "saspgm".

2. Right mouse click on addseq2.sas and select "Batch Submit".

3. Review the addseq2.log and verify that the following messages are produce corresponding to each test.

   • Test (A)
     ERROR: [addseq] specified data data.demog does not exist. 

   • Test (B)
     ERROR: [addseq] The domain must be in ( 
     'AE', 'AU', 'BM', 'BR', 'CM', 'CO', 'CP', 
     'DC', 'DM', 'DR', 'DS', 'DV', 'DY', 'EE', 
     'EG', 'EX', 'FH', 'HU', 'IE', 'IM', 'LB', 
     'MB', 'MH', 'ML', 'NE', 'OM', 'PC', 'PE', 
     'PP', 'QS', 'SC', 'SE', 'SG', 'SK', 'SL', 
     'SS', 'ST', 'SU', 'SV', 'TA', 'TE', 'TI', 
     'TV', 'VS') 

   • Test (C)
     ERROR: [addseq] USUBJID: newid does not exist in dataset. 

   • Test (D)
     ERROR: [addseq] IDVAR: newid does not exist in dataset. 
     

Instructions 3
The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation directory named "saspgm".

2. Right mouse click on addseq3.sas and select "Batch Submit".

3. Review the addseq3.log and verify that the following messages are produce corresponding to each test.

   • Test (A)
     ERROR: The base code path 'K:\addseq\basecode' does not exist. 

   • Test (B)
     ERROR: [addseq] The base code file must be SAS file. 

Instructions 4
The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation sub-directory named 'data\addseq'.

2. Open addseq1 dataset to verify that there are only two variables named "usubjid" and "idvar".

3. Navigate to the validation directory named "saspgm".

4. Right mouse click on addseq4.sas and select "Batch Submit".

5. Review the addseq4.log and verify that there is no error message.

6. Open addseq1 dataset again and verify that aeseq variable is added into dataset.

7. Verify that the sequence number is generated based on each group of usubjid and idvar.

Instructions 5
The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation directory named "saspgm".

2. Right mouse click on addseq5.sas and select "Batch Submit".

3. Review the addseq5.log and verify that there is no error message.

4. Verify that basecode5.sas is generated.

Instructions 6
The following instructions are accomplished through Windows Explorer.

1. Perform instructions 4 before running these instructions.

2. Navigate to the validation directory named "saspgm".

3. Right mouse click on addseq6.sas and select "Batch Submit".

4. Review the addseq6.log and verify that the following message is produced.

   • WARNING: [addseq] Seqvar aeseq exists in dataset. 

5. Navigate to the validation sub-directory named "data\addseq".

6. Verify the time when the dataset is updated to make sure that the addseq1 dataset is still updated.

Instructions 7
The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation directory named "saspgm".

2. Right mouse click on addseq7.sas and select "Batch Submit".

3. Right mouse click and select "Batch Submit" to run the test.

4. Review the addseq7.log and verify that there is no error message.

5. Verify that the addseq.html is created.  This can be verified against the addseq7.html in the benchmark folder.

Instructions 8

The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation sub-directory named "data\addseq\domain".

2. Open from dataset6 to dataset15 to verify that there are only two variables named "usubjid" and "idvar".

3. Navigate to the validation directory named "saspgm".

4. Right mouse click on addseq8.sas and select "Batch Submit".

5. Open addseq8.log to verify that there is no error message.

6. Navigate to the validation sub- directory named "data\addseq\domain".

7. Open from addseq6 to addseq15 to verify that domain is added into datasets.

8. Just keep "usubjid" and "idvar" variables in addseq6 to addseq15.

9. Navigate to the validation directory named "saspgm".

10. Right mouse click on addseq8a.sas and select "Batch Submit".

11. Repeat from step 6 to 9 to check the domain.

12. Right mouse click on addseq8b.sas and select "Batch Submit".

13. Repeat from step 6 to 9 to check the domain.

14. Right mouse click on addseq8c.sas and select "Batch Submit".

15. Repeat from step 6 to 9 to check the domain.

16. Right mouse click on addseq8d.sas and select "Batch Submit".

17. Repeat from step 6 to 9 to check the domain.  Verify that only datasets from addseq6 to addseq10 are updated with the new domains.

Instructions 9
The following instructions are accomplished through Windows Explorer.

1. Navigate to the validation directory named "saspgm".

2. Right mouse click on addseq9.sas and select "Batch Submit".

3. Right mouse click and select "Batch Submit" to run the test.

4. Review the addseq9.log and verify that there is no error message.

5. Navigate to sub-directory named "data\addseq" and verify that datasets "addseq9a" and "addseq9b"  are updated with sequence number and domain.

6. Open there datasets to verify that:
   • addseq9a: the order of the observations is sorted by usubjid.
   • addseq9b: the order of the observations is kept as the original order.

For more information, please contact MXI .